Skip to content

0.11.0 — openkal 0.12.0 - #24

Merged
Sunrisepeak merged 2 commits into
mainfrom
a-unit-a-caller-cannot-name
Aug 31, 2026
Merged

0.11.0 — openkal 0.12.0#24
Sunrisepeak merged 2 commits into
mainfrom
a-unit-a-caller-cannot-name

Conversation

@Sunrisepeak

Copy link
Copy Markdown
Member

No behaviour changes. The specification's 0.12 additions are prose: clause 11
entry 9 now names what handles-do-not-cross costs a caller composing job
control, and the two file-creating operations point at entry 6. This
implementation already satisfied both.

No behaviour changes. The specification's 0.12 additions are prose: clause 11
entry 9 now names what handles-do-not-cross costs a caller composing job
control, and the two file-creating operations point at entry 6. This
implementation already satisfied both.
⚠️ The same defect as openkal-macos, and this one SHIPPED --- in 0.11, where
this operation was added. The result of installing the disposition was
discarded, so an installation that failed would have handed the caller a word
that can never change.

Found by writing the same code for the other kernel, where the trampoline made
the failure mode impossible to overlook. The suite conforms in 181 observations
with the change.
@Sunrisepeak
Sunrisepeak merged commit bd8e7e9 into main Aug 31, 2026
2 checks passed
@Sunrisepeak
Sunrisepeak deleted the a-unit-a-caller-cannot-name branch August 31, 2026 00:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant